docs(contributing): use action verbs for all PR types including docs#99
docs(contributing): use action verbs for all PR types including docs#99angelicawill merged 1 commit intomainfrom
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 6 minutes and 51 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Time Submission Status
You can submit time with the command. Example: See available commands to help comply with our Guidelines. |
|
@holdex pr submit-time 15m |
|
@holdex pr submit-time 5m |
Summary
The naming convention required user-focused action verbs, but this was only illustrated with
feat/fix/testexamples. The singledocsexample (docs(ui): design table component) used a developer-action verb ("design"), which contradicted the rule and made it easy to default to verbs like "document", "update", or "add".Added an explicit warning after the user action verbs list clarifying the rule applies to all PR types, with a
docscounterexample table.